Detecting infinite loops in a programmable atomic transaction

ABSTRACT

Disclosed in some examples are systems, methods, devices, and machine-readable mediums to detect and terminate programmable atomic transactions that are stuck in an infinite loop. In order to detect and terminate these transactions, the programmable atomic unit may use an instruction counter that increments each time an instruction is executed during execution of a programmable atomic transaction. If the instruction counter meets or exceeds a threshold instruction execution limit without reaching the termination instruction, the programmable atomic transaction may be terminated, all resources used (e.g., memory locks) may be freed, and a response may be sent to a calling processor.

STATEMENT REGARDING GOVERNMENT SUPPORT

This invention was made with U.S. Government support under Agreement No. HR00111890003, awarded by DARPA. The U.S. Government has certain rights in the invention.

BACKGROUND

Chiplets are an emerging technique for integrating various processing functionalities. Generally, a chiplet system is made up of discreet modules (each a “chiplet”) that are integrated on an interposer, and in many examples interconnected as desired through one or more established networks, to provide a system with the desired functionality. The interposer and included chiplets may be packaged together to facilitate interconnection with other components of a larger system. Each chiplet may include one or more individual integrated circuits, or “chips” (ICs), potentially in combination with discrete circuit components, and commonly coupled to a respective substrate to facilitate attachment to the interposer. Most or all chiplets in a system will be individually configured for communication through the one or more established networks.

The configuration of chiplets as individual modules of a system is distinct from such a system being implemented on single chips that contain distinct device blocks (e.g., intellectual property (IP) blocks) on one substrate (e.g., single die), such as a system-on-a-chip (SoC), or multiple discrete packaged devices integrated on a printed circuit board (PCB). In general, chiplets provide better performance (e.g., lower power consumption, reduced latency, etc.) than discrete packaged devices, and chiplets provide greater production benefits than single die chips. These production benefits can include higher yields or reduced development costs and time.

Chiplet systems may include, for example, one or more application processor) chiplets and one or more support chiplets. Here, the distinction between application and support chiplets is simply a reference to the likely design scenarios for the chiplet system. Thus, for example, a synthetic vision chiplet system can include, by way of example only, an application chiplet to produce the synthetic vision output along with support chiplets, such as a memory controller chiplet, a sensor interface chiplet, or a communication chiplet. In a typical use case, the synthetic vision designer can design the application chiplet and source the support chiplets from other parties. Thus, the design expenditure (e.g., in terms of time or complexity) is reduced because by avoiding the design and production of functionality embodied in the support chiplets. Chiplets also support the tight integration of IP blocks that can otherwise be difficult, such as those manufactured using different processing technologies or using different feature sizes (or utilizing different contact technologies or spacings). Thus, multiple IC's or IC assemblies, with different physical, electrical, or communication characteristics may be assembled in a modular manner to provide an assembly providing desired functionalities. Chiplet systems can also facilitate adaptation to suit needs of different larger systems into which the chiplet system will be incorporated. In an example, IC's or other assemblies can be optimized for the power, speed, or heat generation for a specific function—as can happen with sensors—can be integrated with other devices more easily than attempting to do so on a single die. Additionally, by reducing the overall size of the die, the yield for chiplets tends to be higher than that of more complex, single die devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure. The drawings, however, should not be taken to limit the disclosure to the specific embodiments, but are for explanation and understanding only.

FIGS. 1A and 1B illustrate an example of a chiplet system, according to some examples of the present disclosure.

FIG. 2 illustrates components of an example of a memory controller chiplet, according to some examples of the present disclosure.

FIG. 3 illustrates components in an example of a programmable atomic unit (PAU), according to some examples of the present disclosure.

FIG. 4 illustrates a request packet for requesting execution of a particular programmable atomic transaction according to some examples of the present disclosure.

FIG. 5 illustrates a programmable atomic transaction response message according to some examples of the present disclosure.

FIG. 6 illustrates a flowchart of a method of handling a request to execute a programmable atomic transaction according to some examples of the present disclosure.

FIG. 7 illustrates a schematic of a memory controller 700 according to some examples of the present disclosure.

FIG. 8 is a block diagram of an example of a machine with which, in which, or by which embodiments of the present disclosure can operate according to some examples of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 , described below, offers an example of a chiplet system and the components operating therein. As explained below, such chiplet systems may include a memory controller that has programmable atomic units that execute programmable atomic transactions that comprise one or more instructions that are executed upon values stored in the memory. These instructions are stored in one or more memory partitions of memory in the programmable atomic unit. Since the programmable atomic unit executes programmable atomic transactions that are customized by one or more processes, the programmable atomic unit has no way of ensuring that the programmable atomic transactions are free of defects that may cause undesired behavior. For example, a programmable atomic transaction with a defect may enter an infinite loop. The calling process may become stuck waiting for the programmable atomic transaction to complete. While the calling process may be programmed to mitigate this by moving on to the next instruction at the expiry of a timer, the programmable atomic unit may still be stuck in the infinite loop. Subsequent calls to the programmable atomic unit by the process, or by other processes may not be serviceable by the programmable atomic unit. Because the programmable atomic unit is a shared resource across multiple processes and in some examples, multiple processors on different chiplets, a programable atomic transaction that enters an infinite loop may affect other processes executing on other processors of the chiplet. Disclosed herein are methods, systems, devices, programmable atomic units, memory controllers, and the like which provide for methods of terminating programmable atomic transactions that have executed more than a determined amount of instructions.

FIGS. 1A and 1B illustrate an example of a chiplet system 110, according to an embodiment. FIG. 1A is a representation of the chiplet system 110 mounted on a peripheral board 105, that can be connected to a broader computer system by a peripheral component interconnect express (PCle), for example. The chiplet system 110 includes a package substrate 115, an interposer 120, and four chiplets, an application chiplet 125, a host interface chiplet 135, a memory controller chiplet 140, and a memory device chiplet 150. Other systems may include many additional chiplets to provide additional functionalities as will be apparent from the following discussion. The package of the chiplet system 110 is illustrated with a lid or cover 165, though other packaging techniques and structures for the chiplet system can be used. FIG. 1B is a block diagram labeling the components in the chiplet system for clarity.

The application chiplet 125 is illustrated as including a network-on-chip (NOC) 130 to support a chiplet network 155 for inter-chiplet communications. In example embodiments NOC 130 may be included on the application chiplet 125. In an example, NOC 130 may be defined in response to selected support chiplets (e.g., chiplets 135, 140, and 150) thus enabling a designer to select an appropriate number or chiplet network connections or switches for the NOC 130. In an example, the NOC 130 can be located on a separate chiplet, or even within the interposer 120. In examples as discussed herein, the NOC 130 implements a chiplet protocol interface (CPI) network.

The CPI is a packet-based network that supports virtual channels to enable a flexible and high-speed interaction between chiplets. CPI enables bridging from intra-chiplet networks to the chiplet network 155. For example, the Advanced eXtensible Interface (AXI) is a widely used specification to design intra-chip communications. AXI specifications, however, cover a great variety of physical design options, such as the number of physical channels, signal timing, power, etc. Within a single chip, these options are generally selected to meet design goals, such as power consumption, speed, etc. However, to achieve the flexibility of the chiplet system, an adapter, such as CPI, is used to interface between the various AXI design options that can be implemented in the various chiplets. By enabling a physical channel to virtual channel mapping and encapsulating time-based signaling with a packetized protocol, CPI bridges intra-chiplet networks across the chiplet network 155.

CPI can use a variety of different physical layers to transmit packets. The physical layer can include simple conductive connections, or can include drivers to increase the voltage, or otherwise facilitate transmitting the signals over longer distances. An example of one such physical layer can include the Advanced Interface Bus (AIB), which in various examples, can be implemented in the interposer 120. AIB transmits and receives data using source synchronous data transfers with a forwarded clock. Packets are transferred across the AIB at single data rate (SDR) or dual data rate (DDR) with respect to the transmitted clock. Various channel widths are supported by AIB. AIB channel widths are in multiples of 20 bits when operated in SDR mode (20, 40, 60, . . . ), and multiples of 40 bits for DDR mode: (40, 80, 120, . . . ). The AIB channel width includes both transmit and receive signals. The channel can be configured to have a symmetrical number of transmit (TX) and receive (RX) input/outputs (I/Os) or have a non-symmetrical number of transmitters and receivers (e.g., either all transmitters or all receivers). The channel can act as an AIB master or slave depending on which chiplet provides the master clock. AlB I/O cells support three clocking modes: asynchronous (i.e. non-clocked), SDR, and DDR. In various examples, the non-clocked mode is used for clocks and some control signals. The SDR mode can use dedicated SDR only I/O cells, or dual use SDR/DDR I/O cells.

In an example, CPI packet protocols (e.g., point-to-point or routable) can use symmetrical receive and transmit I/O cells within an AIB channel. The CPI streaming protocol allows more flexible use of the AIB I/O cells. In an example, an AIB channel for streaming mode can configure the I/O cells as all TX, all RX, or half RX and half RX. CPI packet protocols can use an AIB channel in either SDR or DDR operation modes. In an example, the AIB channel is configured in increments of 80 I/O cells (i.e. 40 TX and 40 RX) for SDR mode and 40 I/O cells for DDR mode. The CPI streaming protocol can use an AIB channel in either SDR or DDR operation modes. Here, in an example, the AIB channel is in increments of 40 I/O cells for both SDR and DDR modes. In an example, each AIB channel is assigned a unique interface identifier. The identifier is used during CPI reset and initialization to determine paired AIB channels across adjacent chiplets. In an example, the interface identifier is a 20-bit value comprising a seven-bit chiplet identifier, a seven-bit column identifier, and a six-bit link identifier. The AIB physical layer transmits the interface identifier using an AIB out-of-band shift register. The 20-bit interface identifier is transferred in both directions across an AIB interface using bits 32-51 of the shift registers.

AIB defines a stacked set of AIB channels as an AIB channel column. An AIB channel column has some number of AIB channels, plus an auxiliary channel. The auxiliary channel contains signals used for AIB initialization. All AIB channels (other than the auxiliary channel) within a column are of the same configuration (e.g., all TX, all RX, or half TX and half RX, as well as having the same number of data I/O signals). In an example, AIB channels are numbered in continuous increasing order starting with the AIB channel adjacent to the AUX channel. The AIB channel adjacent to the AUX is defined to be AIB channel zero.

Generally, CPI interfaces on individual chiplets can include serialization-deserialization (SERDES) hardware. SERDES interconnects work well for scenarios in which high-speed signaling with low signal count are desirable. SERDES, however, can result in additional power consumption and longer latencies for multiplexing and demultiplexing, error detection or correction (e.g., using block level cyclic redundancy checking (CRC)), link-level retry, or forward error correction. However, when low latency or energy consumption is a primary concern for ultra-short reach, chiplet-to-chiplet interconnects, a parallel interface with clock rates that allow data transfer with minimal latency may be utilized. CPI includes elements to minimize both latency and energy consumption in these ultra-short reach chiplet interconnects.

For flow control, CPI employs a credit-based technique. A recipient, such as the application chiplet 125, provides a sender, such as the memory controller chiplet 140, with credits that represent available buffers. In an example, a CPI recipient includes a buffer for each virtual channel for a given time-unit of transmission. Thus, if the CPI recipient supports five messages in time and a single virtual channel, the recipient has five buffers arranged in five rows (e.g., one row for each unit time). If four virtual channels are supported, then the recipient has twenty buffers arranged in five rows. Each buffer holds the payload of one CPI packet.

When the sender transmits to the recipient, the sender decrements the available credits based on the transmission. Once all credits for the recipient are consumed, the sender stops sending packets to the recipient. This ensures that the recipient always has an available buffer to store the transmission.

As the recipient processes received packets and frees buffers, the recipient communicates the available buffer space back to the sender. This credit return can then be used by the sender allow transmitting of additional information.

Also illustrated is a chiplet mesh network 160 that uses a direct, chiplet-to-chiplet technique without the need for the NOC 130. The chiplet mesh network 160 can be implemented in CPI, or another chiplet-to-chiplet protocol. The chiplet mesh network 160 generally enables a pipeline of chiplets where one chiplet serves as the interface to the pipeline while other chiplets in the pipeline interface only with themselves.

Additionally, dedicated device interfaces, such as one or more industry standard memory interfaces 145 (such as, for example, synchronous memory interfaces, such as DDR5, DDR 6), can also be used to interconnect chiplets. Connection of a chiplet system or individual chiplets to external devices (such as a larger system can be through a desired interface (for example, a PCIE interface). Such as external interface may be implemented, in an example, through a host interface chiplet 135, which in the depicted example, provides a PCIE interface external to chiplet system 110. Such dedicated interfaces 145 are generally employed when a convention or standard in the industry has converged on such an interface. The illustrated example of a Double Data Rate (DDR) interface 145 connecting the memory controller chiplet 140 to a dynamic random access memory (DRAM) memory device 150 is just such an industry convention.

Of the variety of possible support chiplets, the memory controller chiplet 140 is likely present in the chiplet system 110 due to the near omnipresent use of storage for computer processing as well as sophisticated state-of-the-art for memory devices. Thus, using memory device chiplets 150 and memory controller chiplets 140 produced by others gives chiplet system designers access to robust products by sophisticated producers. Generally, the memory controller chiplet 140 provides a memory device specific interface to read, write, or erase data. Often, the memory controller chiplet 140 can provide additional features, such as error detection, error correction, maintenance operations, or atomic operation execution. For some types of memory, maintenance operations tend to be specific to the memory device 150, such as garbage collection in NAND flash or storage class memories, temperature adjustments (e.g., cross temperature management) in NAND flash memories. In an example, the maintenance operations can include logical-to-physical (L2P) mapping or management to provide a level of indirection between the physical and logical representation of data. In other types of memory, for example DRAM, some memory operations, such as refresh may be controlled by a host processor or of a memory controller at some times, and at other times controlled by the DRAM memory device, or by logic associated with one or more DRAM devices, such as an interface chip (in an example, a buffer).

Atomic transactions are one or more data manipulation operations that, for example, may be performed by the memory controller chiplet 140. In other chiplet systems, the atomic transactions may be performed by other chiplets. For example, an atomic transaction of “increment” can be specified in a command by the application chiplet 125, the command including a memory address and possibly an increment value. Upon receiving the command, the memory controller chiplet 140 retrieves a number from the specified memory address, increments the number by the amount specified in the command, and stores the result. Upon a successful completion, the memory controller chiplet 140 provides an indication of the commands success to the application chiplet 125. Atomic transactions avoid transmitting the data across the chiplet mesh network 160, resulting in lower latency execution of such commands.

Atomic transactions can be classified as built-in atomics or programmable (e.g., custom) atomic transactions. Built-in atomic transactions are a finite set of operations that are immutably implemented in hardware. Programmable atomic transactions are small programs with one or more instructions (e.g., an instruction set) that may execute on a programmable atomic unit (PAU) (e.g., a custom atomic unit (CAU)) of the memory controller chiplet 140. FIG. 1 illustrates an example of a memory controller chiplet that discusses a PAU.

The memory device chiplet 150 can be, or include any combination of, volatile memory devices or non-volatile memories. Examples of volatile memory devices include, but are not limited to, random access memory (RAM)—such as DRAM) synchronous DRAM (SDRAM), graphics double data rate type 6 SDRAM (GDDR6 SDRAM), among others. Examples of non-volatile memory devices include, but are not limited to, negative-and-(NAND)-type flash memory, storage class memory (e.g., phase-change memory or memristor based technologies), ferroelectric RAM (FeRAM), among others. The illustrated example includes the memory device 150 as a chiplet, however, the memory device 150 can reside elsewhere, such as in a different package on the peripheral board 105. For many applications, multiple memory device chiplets may be provided. In an example, these memory device chiplets may each implement one or multiple storage technologies. In an example, a memory chiplet may include, multiple stacked memory die of different technologies, for example one or more SRAM devices stacked or otherwise in communication with one or more DRAM devices. Memory controller 140 may also serve to coordinate operations between multiple memory chiplets in chiplet system 110; for example, to utilize one or more memory chiplets in one or more levels of cache storage, and to use one or more additional memory chiplets as main memory. Chiplet system 110 may also include multiple memory controllers 140, as may be used to provide memory control functionality for separate processors, sensors, networks, etc. A chiplet architecture, such as chiplet system 110 offers advantages in allowing adaptation to different memory storage technologies; and different memory interfaces, through updated chiplet configurations, without requiring redesign of the remainder of the system structure.

FIG. 2 illustrates components of an example of a memory controller chiplet 205, according to an embodiment. The memory controller chiplet 205 includes a cache 210, a cache controller 215, an off-die memory controller 220 (e.g., to communicate with off-die memory 275), a network communication interface 225 (e.g., to interface with a chiplet network 285 and communicate with other chiplets), and a set of atomic and merge unit 250. Members of this set can include, for example, a write merge unit 255, a memory hazard unit 260, built-in atomic unit 265 (for performing built in atomic transactions), or a programmable atomic unit (PAID) 270 (for performing programmable atomic transactions). The various components are illustrated logically, and not as they necessarily would be implemented. For example, the built-in atomic unit 265 likely comprises different devices along a path to the off-die memory. For example, the built-in atomic unit 265 could be in an interface device/buffer on a memory chiplet, as discussed above. In contrast, the programmable atomic unit 270 could be implemented in a separate processor on the memory controller chiplet 205 (but in various examples may be implemented in other locations, for example on a memory chiplet).

The off-die memory controller 220 is directly coupled to the off-die memory 275 (e.g., via a bus or other communication connection) to provide write operations and read operations to and from the one or more off-die memory, such as off-die memory 275 and off-die memory 280. In the depicted example, the off-die memory controller 220 is also coupled for output to the atomic and merge unit 250, and for input to the cache controller 215 (e.g., a memory side cache controller).

In the example configuration, cache controller 215 is directly coupled to the cache 210, and may be coupled to the network communication interface 225 for input (such as incoming read or write requests), and coupled for output to the off-die memory controller 220.

The network communication interface 225 includes a packet decoder 230, network input queues 235, a packet encoder 240, and network output queues 245 to support a packet-based chiplet network 285, such as CPI. The chiplet network 285 can provide packet routing between and among processors, memory controllers, hybrid threading processors, configurable processing circuits, or communication interfaces. In such a packet-based communication system, each packet typically includes destination and source addressing, along with any data payload or instruction. In an example, the chiplet network 285 can be implemented as a collection of crossbar switches having a folded Clos configuration, or a mesh network providing for additional connections, depending upon the configuration.

In various examples, the chiplet network 285 can be part of an asynchronous switching fabric. Here, a data packet can be routed along any of various paths, such that the arrival of any selected data packet at an addressed destination can occur at any of multiple different times, depending upon the routing. Additionally, chiplet network 285 can be implemented at least in part as a synchronous communication network, such as a synchronous mesh communication network. Both configurations of communication networks are contemplated for use for examples in accordance with the present disclosure.

The memory controller chiplet 205 can receive a packet having, for example, a source address, a read request, and a physical address. In response, the off-die memory controller 220 or the cache controller 215 will read the data from the specified physical address (which can be in the off-die memory 275 or in the cache 210), and assemble a response packet to the source address containing the requested data. Similarly, the memory controller chiplet 205 can receive a packet having a source address, a write request, and a physical address. In response, the memory controller chiplet 205 will write the data to the specified physical address (which can be in the cache 210 or in the off-die memories 275 or 280), and assemble a response packet to the source address containing an acknowledgement that the data was stored to a memory.

Thus, the memory controller chiplet 205 can receive read and write requests via the chiplet network 285 and process the requests using the cache controller 215 interfacing with the cache 210, if possible. If the request cannot be handled by the cache controller 215, the off-die memory controller 220 handles the request by communication with the off-die memories 275 or 280, the atomic and merge unit 250, or both. As noted above, one or more levels of cache may also be implemented in off-die memories 275 or 280; and in some such examples may be accessed directly by cache controller 215. Data read by the off-die memory controller 220 can be cached in the cache 210 by the cache controller 215 for later use.

The atomic and merge unit 250 are coupled to receive (as input) the output of the off-die memory controller 220, and to provide output to the cache 210, the network communication interface 225, or directly to the chiplet network 285. The memory hazard unit 260, write merge unit 255 and the built-in (e.g., predetermined) atomic unit 265 can each be implemented as state machines with other combinational logic circuitry (such as adders, shifters, comparators, AND gates, OR gates, XOR gates, or any suitable combination thereof) or other logic circuitry. These components can also include one or more registers or buffers to store operand or other data. The PAU 270 can be implemented as one or more processor cores or control circuitry, and various state machines with other combinational logic circuitry or other logic circuitry, and can also include one or more registers, buffers, or memories to store addresses, executable instructions, operand and other data, or can be implemented as a processor. An example PAU 270 is shown in FIG.

The write merge unit 255 receives read data and request data, and merges the request data and read data to create a single unit having the read data and the source address to be used in the response or return data packet). The write merge unit 255 provides the merged data to the write port of the cache 210 (or, equivalently, to the cache controller 215 to write to the cache 210). Optionally, the write merge unit 255 provides the merged data to the network communication interface 225 to encode and prepare a response or return data packet for transmission on the chiplet network 285.

When the request data is for a built-in atomic operation, the built-in atomic unit 265 receives the request and reads data, either from the write merge unit 255 or directly from the off-die memory controller 220. The atomic transaction is performed, and using the write merge unit 255, the resulting data is written to the cache 210, or provided to the network communication interface 225 to encode and prepare a response or return data packet for transmission on the chiplet network 285.

The built-in atomic unit 265 handles predefined atomic transactions such as fetch-and-increment or compare-and-swap. In an example, these transactions perform a simple read-modify-write operation to a single memory location of 32-bytes or less in size. Atomic memory transactions are initiated from a request packet transmitted over the chiplet network 285. The request packet has a physical address, atomic operator type, operand size, and optionally up to 32-bytes of data. The atomic transaction performs the read-modify-write to a cache memory line of the cache 210, filling the cache memory if necessary. The atomic transaction response can be a simple completion response, or a response with up to 32-bytes of data. Example atomic memory transactions include fetch-and-AND, fetch-and-OR, fetch-and-XOR, fetch-and-add, fetch-and-subtract, fetch-and-increment, fetch-and-decrement, fetch-and-minimum, fetch-and-maximum, fetch-and-swap, and compare-and-swap. In various example embodiments, 32-bit and 64-bit operations are supported, along with operations on 16 or 32 bytes of data. Methods disclosed herein are also compatible with hardware supporting larger or smaller operations and more or less data.

Built-in atomic transactions can also involve requests for a “standard” atomic standard on the requested data, such as comparatively simple, single cycle, integer atomics—such as fetch-and-increment or compare-and-swap—which will occur with the same throughput as a regular memory read or write operation not involving an atomic operation. For these operations, the cache controller 215 may generally reserve a cache line in the cache 210 by setting a hazard bit (in hardware), so that the cache line cannot be read by another process while it is in transition. The data is obtained from either the off-die memory 275 or the cache 210, and is provided to the built-in atomic unit 265 to perform the requested atomic transaction. Following the atomic transaction, in addition to providing the resulting data to the packet encoder 240 to encode outgoing data packets for transmission on the chiplet network 285, the built-in atomic unit 265 provides the resulting data to the write merge unit 255, which will also write the resulting data to the cache 210. Following the writing of the resulting data to the cache 210, any corresponding hazard bit which was set will be cleared by the memory hazard unit 260.

The PAU 270 enables high performance (high throughput and low latency) for programmable atomic transactions (also referred to as “custom atomic transactions” or “custom atomic operations”), comparable to the performance of built-in atomic transactions. Rather than executing multiple memory accesses, in response to an atomic transaction request designating a programmable atomic transaction and a memory address, circuitry in the memory controller chiplet 205 transfers the atomic transaction request to PAU 270 and sets a hazard bit stored in a memory hazard register corresponding to the memory address of the memory line used in the atomic operation, to ensure that no other operation (read, write, or atomic transaction) is performed on that memory line, which hazard bit is then cleared upon completion of the atomic transaction. Additional, direct data paths provided for the PAU 270 executing the programmable atomic transactions allow for additional write operations without any limitations imposed by the bandwidth of the communication networks and without increasing any congestion of the communication networks.

The PAU 270 includes a multi-threaded processor 320, for example, such as a RISC-V ISA based multi-threaded processor, having one or more processor cores, and further having an extended instruction set for executing programmable atomic transactions. When provided with the extended instruction set for executing programmable atomic transactions, the processor 320 of PAU 270 can be embodied as one or more hybrid threading processors. In some example embodiments, the processor 320 of PAU 270 provides barrel-style, round-robin instantaneous thread switching to maintain a high instruction-per-clock rate.

PAU 270 may include a local memory 305, such as Static Random-Access Memory (SRAM), NAND, phase change memory, or the like. The local memory 305 may include registers 335, instruction memory 325, and cache 330. The local memory 305 may be accessible to the processor 320 through a memory controller 310.

Programmable atomic transactions can be performed by the PAU 270 involving requests for programmable atomic transactions on the requested data. A user can prepare programming code in the form of one or more instructions to provide such programmable atomic transactions. For example, the programmable atomic transactions can be comparatively simple, multi-cycle operations such as floating-point addition, or comparatively complex, multi-instruction operations such as a Bloom filter insert. The programmable atomic transactions can be the same as or different than the predetermined atomic transactions, insofar as they are defined by the user rather than a system vendor. For these operations, the cache controller 215 can reserve a cache line in the cache 210, by setting a hazard bit (in hardware), so that cache line cannot be read by another process while it is in transition. The data is obtained from either the cache 210 or the off-die memories 275 or 280, and is provided to the PAU 270 to perform the requested programmable atomic transaction. Following the atomic operation, the PAU 270 will provide the resulting data to the network communication interface 225 to directly encode outgoing data packets having the resulting data for transmission on the chiplet network 285. In addition, the PAU 270 will provide the resulting data to the cache controller 215, which will also write the resulting data to the cache 210. Following the writing of the resulting data to the cache 210, any corresponding hazard bit which was set will be cleared by the cache controller 215.

In selected examples, the approach taken for programmable atomic transactions is to provide multiple, generic, programmable atomic transaction request types that can be sent through the chiplet network 285 to the memory controller chiplet 205 from an originating source such as a processor or other system component. The cache controllers 215 or off-die memory controller 220 identify the request as a programmable atomic transaction and forward the request to the PAU 270. In a representative embodiment, the PAU 270: (1) is a programmable processing element capable of efficiently performing a user defined atomic transaction; (2) can perform load and stores to memory, arithmetic and logical operations and control flow decisions; and (3) leverages the RISC-V ISA with a set of new, specialized instructions to facilitate interacting with such controllers 215, 220 to atomically perform the user-defined transaction. In desirable examples, the RISC-V ISA contains a full set of instructions that support high level language operators and data types. The PAU 270 can leverage the RISC-V ISA, but will commonly support a more limited set of instructions and limited register file size to reduce the die size of the unit when included within the memory controller chiplet 205.

As mentioned above, prior to the writing of the read data to the cache 210, the set hazard bit for the reserved cache line is to be cleared, by the memory hazard unit 260. Accordingly, when the request and read data is received by the write merge unit 255, a reset or clear signal can be transmitted by the memory hazard unit 260 to the cache 210 to reset the set memory hazard bit for the reserved cache line. Also, resetting this hazard bit will also release a pending read or write request involving the designated (or reserved) cache line, providing the pending read or write request to an inbound request multiplexer for selection and processing.

FIG. 3 illustrates a block diagram of a programmable atomic unit 270 according to some examples of the present disclosure. As previously described, programmable atomic units may include one or more programmable atomic transactions that are specified by sets of one or more atomic instructions stored in instruction memory 325 that are custom defined and perform operations on memory managed by the memory controller. The instructions of atomic transactions may be specified by applications and/or processes outside the programmable atomic unit 270 that may reside on the memory controller chiplet 205, other chiplets (such as application chiplet 125), or an off chiplet-device. In some examples, the instructions of the programmable atomic transaction are loaded by the operating system when registered by a process. To execute the programmable atomic transaction, the initiating process sends a CPI message including an instruction to execute the requested programmable atomic transaction on the local memory 305 of the programmable atomic unit 270 by providing an index into the local memory of the programmable atomic unit 270. The programmable atomic transactions may utilize cache 330, registers 335, and other memory of local memory 305 during execution. Local memory controller 310 may manage the local memory 305. In some examples, programmable atomic unit 270 may not need the local memory controller as the local memory 305 may be SRAM.

As previously described, improper programming can cause the programmable atomic transaction to enter an infinite loop which may tie up some or all of the resources of the programmable atomic unit. For example, the programmable atomic transaction may be rendered unusable for all processes until a restart of the system. As such, a method of detecting and terminating a programmable atomic transaction that is stuck in an infinite loop is desired. As used herein an infinite loop is defined as a series of instructions that repetitively execute and one or more conditions necessary for ceasing such repetition do not occur.

For typical computing systems infinite loops may be detected by users of the system and terminated by the users using the operating system (e.g., through a task manager or through a command such as control-c). For embedded systems, detection of a program that is stuck in an infinite loop is more challenging. Given the desires of the programmable atomic unit in providing low latency operations, methods to detect and recover from infinite loops must do so without significantly increasing overhead. One possible solution might be a timeout timer. The programmable atomic transaction would be terminated if it does not finish prior to the timer expiry. Due to the customizable nature of these transactions, and due to the possibility that the programmable atomic transaction may need to wait for resources during execution, choosing an appropriate timeout value may be difficult.

Disclosed in some examples are systems, methods, devices, and machine-readable mediums to detect and terminate programmable atomic transactions that are stuck in an infinite loop with minimal impact to latency and hardware design. In order to detect and terminate these transactions, the programmable atomic unit may use an instruction counter that increments each time an instruction is executed during execution of a programmable atomic transaction. At the beginning of the programmable atomic transaction, the instruction counter is reset to zero and every instruction executed until a termination instruction increments the instruction counter by one. If a termination instruction is executed, the execution of the programmable atomic transaction is complete, and a response is generated. If the instruction counter meets or exceeds a threshold instruction execution limit without reaching the termination instruction, the programmable atomic transaction may be terminated, all resources used (e.g., memory locks) may be freed, and a response may be sent to a calling processor.

The instruction execution limit may be set by the programmable atomic unit, by the processor that registers the programmable atomic unit, by the programmer of the programmable atomic unit, or the like. For example, during registration the process that registers the programmable atomic unit (e.g., the operating system) may supply an instruction execution limit. In other examples, the programmable atomic unit may determine the instruction execution limit. As noted, the instruction execution limit may be stored with other information about the programmable atomic transaction.

In some examples, the instruction execution limit may be a global threshold that is the same across all programmable atomic transactions. In these examples, it may be set to be a reasonably high threshold (e.g., greater than the number of instructions that can be stored in the instruction memory of the programmable atomic unit).

In other examples, the instruction execution limit may be set based upon an analysis of the programmable atomic transactions during registration or execution of the programmable atomic transaction. This analysis may determine a count of the number of instructions in the programmable atomic transaction. The programmable atomic unit or by the process or operating system registering the programmable atomic transaction may perform this analysis. The instruction count may be approximated based upon the number of segments that are used by the programmable atomic transaction or may be an actual count of the number of instructions. For the approximation of the number of instructions, the number of instructions may be approximated based upon the number of partitions that the programmable atomic unit takes up and the number of instructions that fit into the partition. For example, if the partition stores 32 instructions and the programmable atomic transaction takes up two partitions, the number of instructions may be 64.

For examples in which an actual count is used, in some examples the system may count each instruction as a single instruction regardless of loops and conditional statements. The simple count starts at the first instruction and increments a counter until an “end” is found. Loops are counted as a single instruction and the code that is looped is counted once. Conditional statements are counted as one instruction and both branches are counted.

The instruction execution limit may be equal to the number of instructions that were counted or may be larger or smaller than the number of instructions that were counted. For example, it may be anticipated that some instructions may be performed more than once in loops, or as a result of busy shared resources (e.g., the instruction is retried). In other examples, it may be anticipated that some branches of instructions may only be conditionally executed and thus the instruction execution limit may be less than the total number of instructions counted. In some examples, the instruction execution limit may be a function of the number of instructions in the programmable atomic transaction. For example, the instruction execution limit may be set to be twice the number of instructions in the programmable atomic transactions.

As previously described, the instruction execution limit may be determined and supplied by a process or operating system when registering a programmable atomic transaction with the memory controller. As previously described, the instruction memory of the programmable atomic unit may be partitioned into contiguous blocks called partitions. Each partition may hold a number of instructions (e.g., 32 instructions) and may be managed by the operating system. The operating system may track which partitions are free and which are used by which programmable atomic transactions.

A process desiring to call a programmable atomic transaction first registers the programmable atomic transaction by calling one or more functions of an operating system through an application programming interface (API). The function call of the API may include the instructions (or a location of the instructions) to load. The operating system may first determine a size needed to hold the instructions (e.g., by counting the number of instructions that are provided) and use the determined size to locate a series of one or more contiguous free partitions of instruction memory (e.g., instruction memory 325) in the programmable atomic unit that are large enough to hold the programmable atomic transaction's instructions. The first partition index in that instruction block corresponds to a system unique index (SCAID) that globally identifies that programmable atomic transaction. The operating system then loads instructions to the selected memory partitions of the programmable atomic unit. As noted, the operating system or the process may supply the instruction execution limit as part of loading the instructions to the programmable atomic unit. In some examples, the instruction execution limit may be supplied with the request to perform the programmable atomic transaction. The instruction execution limit may be determined by the operating system or the calling process.

As previously described, when requesting execution of a particular programmable atomic transaction the processor executing the process that is requesting the programmable atomic transaction forms a request packet and sends it to the programmable atomic unit. The request packet may include the particular memory location (e.g., partition(s) within local memory 305) identified by the SCAlD, a location of the memory managed by the memory controller chiplet 205 (e.g., off-die memory 275, 280) that is to be operated upon, and one or more arguments. This message is then sent to the memory controller, upon receipt of the message, the processor (e.g., processor 320) of the programmable atomic unit then begins executing the instructions at the indicated partition. That is, the first instruction at the indicated partition is executed.

FIG. 4 illustrates an example request packet for requesting execution of a particular programmable atomic transaction. The fields are described as:

Field Field Name Width Value Description CMD 8 126 Extended VC1 LEN 5 Packet Length SC 1 0 Sequence Continue (ignored for EMD) DID 12 Destination NOC endpoint PATH 8 Endpoint Offset <14:7> CP 2 1 Credit/Path Order-Credit Return enabled in flits 3-N and Path field based path ordering TU 2 Transaction ID <9:8> EpOFF<6:0> 7 Endpoint Offset <6:0> TA 8 Transaction ID <7:0> EPOffset 19 Endpoint Offset <33:15> <33:15> EXCMD 8 Extended Command BTYPE 4 8 BTYPE of 8 is EMD vendor defined SID 12 Source NOC endpoint EPOFFSET 4 Endpoint Offset <37:34> <37:34> RSV 4 0 Reserved CR/RSV 4 Credit Return CrPKnd 4 Credit pool kind CrPIdx 8 Credit Pool Index RSV 4 0 Reserved CaPIdx 8 Custom Atomic Partition Index CaIntv 8 Interleave Size CR/RSV 4 Credit Return DATA 32 Argument Data: 0, 1, 2, or 4 64 Bit Values CR/RSV 4 Credit Return

As noted, a programmable atomic transaction begins by executing the first instruction located at the partition in the instruction RAM (e.g., local memory 305 of programmable atomic unit 270) of the programmable atomic transaction specified by the Custom Atomic Partition Index (CaPIdx) (the SCAID). The operation starts at the first instruction within the partition. The CaPIdx may also be used to index into a control structure that contains additional information for the operation. The additional information includes a flag to indicate whether the transaction is valid, the number of partitions for the transaction, an instruction execution limit, and the like. The number of partitions is used to validate that an operation is executing within the appropriate partitions. An exception is detected, and the executing operation is terminated if the programmable atomic unit detects execution in an inappropriate partition or detects that the number of instructions that have executed exceeds the instruction execution limit.

A response to the programmable atomic transaction is provided as a memory response. In some examples, the response has a status field that indicates whether the operation successfully completed or not. For example, FIG. 5 illustrates the response message. The fields of the response message are as follows:

Field Name Field Width Description CMD 8 Packet command LEN 5 Encoded Packet Length SC 1 Sequence Continue. When set, this packet is part of a multi-packet transfer and this packet is not the last packet in the sequence. This bit is present in the first flit of all packet types DID 8 Destination Endpoint ID bits 7:0-destination fabric endpoint STAT 4 Response Status Path 8 The Path field is used to specify a path through a CPI fabric to force ordering between packets. For both CPI native and AXI over CPI the read response packet's PATH field contains the TID value CP 2 Credit Present/Path Ordering. The CP field contains an encoded value that specifies both if field CR of flits 3-N of the packet contains credit return information as well as whether path ordering is enabled. Data 32 Read response data-bits N*8-1:0 CR/RSV 4 Credit Return Information RSV 4 Reserved

FIG. 6 illustrates a flowchart of a method of executing instructions of the programmable atomic transaction according to some examples of the present disclosure. At operation 605 a request to execute a programmable atomic transaction is received. In some examples, once the programmable atomic transaction unit is ready to execute the requested transaction a program counter (PC) is initialized to the first instruction of the partition given in the request and an instruction counter may be reset to zero. At operation 607, an instruction execution limit may be determined. For example, the instruction execution limit may be determined by reading the value of the instruction execution limit from a table of transaction information associated with the programmable atomic transaction. In some examples, the partition index may also be used to index into a control structure that contains the additional information for the programmable atomic transaction. The additional information may include the instruction execution limit, a flag to indicate whether the transaction is valid, the number of partitions for the transaction, and the like.

At operation 610 a determination is made to determine if an instruction is present at the memory location pointed to by the program counter. In some examples, the program counter may be a register storing an instruction of the currently executing instruction. If there is not an instruction present at that location, a response with an error status code is sent to the calling processor at operation 645. If the instruction is present, then at operation 615 it is determined whether the instruction is a termination instruction. If the instruction is a termination instruction, then the custom atomic transaction is terminated, any locks are released, clean-up is performed, and at operation 650 a response is sent with a normal status code. If the instruction is not a termination instruction, then at operation 620, the instruction is executed. For example, a memory read, an increment, a decrement, a mathematical operation, a memory write, or the like. At operation 625 the instruction counter is incremented. At operation 630 the program counter is incremented to the next instruction in the memory of the programmable atomic transaction.

At operation 635 a check is made to determine whether the program counter is now pointing to an instruction that is in a partition with an index that is past the partition index in which the programmable atomic transaction started and the partition count. For example, if the partition in the request is partition 1, and the maximum partitions provided is 3, and if the instruction lies within partition 5, then the instruction is illegal. If the program counter is pointing to an illegal instruction, then an error is sent to the calling processor at operation 645. Otherwise, flow proceeds to operation 640.

At operation 640, a check is made to determine whether an instruction counter is less than the instruction execution limit. As noted, this prevents infinite loops. If the instruction counter is greater than or equal to the instruction execution limit, the programmable atomic transaction is terminated, locks and other resources are released, and an error is sent to the calling processor at operation 645. For example, the programmable atomic transaction unit may force execution of the termination instruction instead of a next instruction in the programmable atomic transaction. Otherwise, flow of the method proceeds to operation 610 where the next instruction is checked and potentially executed.

FIG. 7 illustrates a schematic of a memory controller 700 according to some examples of the present disclosure. FIG. 7 is another example of a memory controller chiplet 205 and shows many of the same components as shown in FIG. 2 . For example, the cache 720 and 785 are examples of cache 210; DRAM(s) 745 are examples of off-die memory 275-280; atomic/write merge 780 and the programmable atomic unit 795 may be an example of atomics and merge unit 250; other components of FIG. 7 may be examples of other components of FIG. 2 such as off-die memory controller 220 and cache controller 215. NOC Request Queue 705 receives requests from the network-on-chip and provides a small amount of queuing. Atomic Request Queue 710 receives requests from the programmable atomic unit and provides a small amount of queuing. Inbound Request Multiplexer (IRM) 715 selects between inbound memory request sources. The three sources, in order of priority are: Memory Hazard Requests, Atomic Requests, and Inbound NOC Requests. Cache (Read) 720 and Cache (Write) 785 is an SRAM data cache. The diagram shows the cache as two separate blocks (720 and 785), one providing read access, the other providing write access. Delay Block 725 provides one or more pipeline stages to mimic the delay for an SRAM cache read operation. A cache miss requires access to memory to bring the desired data into the cache. During this DRAM access time, the memory line is not available for other requests. The Memory Hazard block (Set block 730 and Clear block 790) maintains a table of hazard bits indicating which memory lines are unavailable for access. An inbound request that tries to access a line with a hazard is held by the Memory Hazard block until the hazard is cleared. Once the hazard is cleared then the request is resent through the Inbound Request Multiplexer. The memory line tag address is hashed to a hazard bit index. The number of hazard bits may be chosen to set the hazard collision probability to a sufficiently low level. Inbound DRAM Control Multiplexer (IDCM) 735 selects from an inbound NOC request and a cache eviction request. Bank Request Queues 740 each separately managed DRAM bank has a dedicated bank request queue to hold requests until they can be scheduled on the associated DRAM bank.

Scheduler 742 selects across the bank queues 740 to choose a request for an available DRAM bank. The DRAM(s) 745 represents the external DRAM device or devices. Request Hit Data Queue 750 holds request data from cache hits until selected. Request Miss Data Queue 755 holds data read from the DRAM(s) until selected. Miss Request Queue 760 is used to hold request packet information for cache misses until the request is selected. Hit Request Queue 765 holds request packet information for cache hits until selected. Data Selection Multiplexer (DSM) 770 selects between DRAM read data and cache hit read data. The selected data is written to the SRAM cache. Request Selection Multiplexer (RSM) 775 selects between hit and miss request queues 760 and 765.

Atomic/Write Merge 780 either merges the request data and DRAM read data, or, if the request is a built-in atomic, the memory data and request data are used as inputs for an atomic operation. Cache (Write) block 785 represents the write port for the SRAM cache. Data from a NOC write request and data from DRAM read operations are written to the SRAM cache. Memory Hazard (Clear) block 790 represents the hazard clear operation for the memory hazard structure. Clearing a hazard may release a pending NOC request and send it to the Inbound Request Multiplexer. Programmable Atomic Unit 795 processes programmable atomic transactions. NOC Outbound Response Multiplexer (ORM) 797 selects between memory controller responses and custom atomic unit responses and sends the selection to the NOC.

FIG. 8 illustrates a block diagram of an example machine 800 with which, in which, or by which any one or more of the techniques (e.g., methodologies) discussed herein can be implemented. Examples, as described herein, can include, or can operate by, logic or a number of components, or mechanisms in the machine 800. Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the machine 800 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership can be flexible over time. Circuitries include members that can, alone or in combination, perform specified operations when operating. In an example, hardware of the circuitry can be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuitry can include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation. Accordingly, in an example, the machine-readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating. In an example, any of the physical components can be used in more than one member of more than one circuitry. For example, under operation, execution units can be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the machine 800 follow.

In alternative embodiments, the machine 800 can operate as a standalone device or can be connected (e.g., networked) to other machines. In a networked deployment, the machine 800 can operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 800 can act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 800 can be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

The machine (e.g., computer system) 800 can include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) 806, and mass storage 808 (e.g., hard drives, tape drives, flash storage, or other block devices) some or all of which can communicate with each other via an interlink (e.g., bus) 830. The machine 800 can further include a display unit 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse). In an example, the display unit 810, input device 812 and UI navigation device 814 can be a touch screen display. The machine 800 can additionally include a mass storage (e.g., drive unit) 808, a signal generation device 818 (e.g., a speaker), a network interface device 820, and one or more sensors 816, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 800 can include an output controller 828, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

Registers of the processor 802, the main memory 804, the static memory 806, or the mass storage 808 can be, or include, a machine readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 824 can also reside, completely or at least partially, within any of registers of the processor 802, the main memory 804, the static memory 806, or the mass storage 808 during execution thereof by the machine 800. In an example, one or any combination of the hardware processor 802, the main memory 804, the static memory 806, or the mass storage 808 can constitute the machine readable medium 822. While the machine readable medium 822 is illustrated as a single medium, the term “machine readable medium” can include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) configured to store the one or more instructions 824.

The term “machine readable medium” can include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and that cause the machine 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples can include solid-state memories, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon-based signals, sound signals, etc.). In an example, a non-transitory machine-readable medium comprises a machine-readable medium with a plurality of particles having invariant (e.g., rest) mass, and thus are compositions of matter. Accordingly, non-transitory machine-readable media are machine readable media that do not include transitory propagating signals. Specific examples of non-transitory machine readable media can include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

In an example, information stored or otherwise provided on the machine readable medium 822 can be representative of the instructions 824, such as instructions 824 themselves or a format from which the instructions 824 can be derived. This format from which the instructions 824 can be derived can include source code, encoded instructions (e.g., in compressed or encrypted form), packaged instructions (e.g., split into multiple packages), or the like. The information representative of the instructions 824 in the machine readable medium 822 can be processed by processing circuitry into the instructions to implement any of the operations discussed herein. For example, deriving the instructions 824 from the information (e.g., processing by the processing circuitry) can include: compiling (e.g., from source code, object code, etc.), interpreting, loading, organizing (e.g., dynamically or statically linking), encoding, decoding, encrypting, unencrypting, packaging, unpackaging, or otherwise manipulating the information into the instructions 824.

In an example, the derivation of the instructions 824 can include assembly, compilation, or interpretation of the information (e.g., by the processing circuitry) to create the instructions 824 from some intermediate or preprocessed format provided by the machine readable medium 822. The information, when provided in multiple parts, can be combined, unpacked, and modified to create the instructions 824. For example, the information can be in multiple compressed source code packages (or object code, or binary executable code, etc.) on one or several remote servers. The source code packages can be encrypted when in transit over a network and decrypted, uncompressed, assembled (e.g., linked) if necessary, and compiled or interpreted (e.g., into a library, stand-alone executable etc.) at a local machine, and executed by the local machine.

The instructions 824 can be further transmitted or received over a communications network 826 using a transmission medium via the network interface device 820 utilizing any one of a number of transfer protocols (e.g., frame relay, Internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks can include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 820 can include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 826. In an example, the network interface device 820 can include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 800, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software. A transmission medium is a machine readable medium. To better illustrate the methods and apparatuses described herein, a non-limiting set of Example embodiments are set forth below as numerically identified Examples.

Other Notes and Examples

Example 1 is an apparatus comprising: A memory controller, a memory array coupled to the memory controller; a programmable atomic unit coupled to the memory controller and comprising a processor, the processor configured to: receive a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index for a partition in a memory of the programmable atomic unit; execute instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and send a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.

In Example 2, the subject matter of Example 1 includes, wherein the processor is further configured to: determine an instruction execution limit for the programmable atomic transaction; initialize an instruction counter; determine whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to a determination that the instruction counter exceeds the instruction execution limit, terminate execution of the programmable atomic transaction.

In Example 3, the subject matter of Examples 1-2 includes, wherein the processor being configured to determine the instruction execution limit comprises being configured to: determine a programmable atomic transaction information data structure from the partition index; and determine the instruction execution limit from the programmable atomic transaction information data structure.

In Example 4, the subject matter of Examples 1-3 includes, wherein the processor is further configured to, prior to receipt of the request packet, receive a request to store instructions in the partition, the request including the instruction execution limit.

In Example 5, the subject matter of Examples 1-4 includes, wherein the processor is configured to determine the instruction execution limit by being configured to: Identify the instruction execution limit from the request packet.

In Example 6, the subject matter of Examples 1-5 includes, wherein the processor is configured to terminate execution of the programmable atomic transaction by being configured to release a lock on a memory location controlled by the memory controller.

In Example 7, the subject matter of Examples 1-6 includes, wherein the processor is configured to determine the instruction execution limit by being configured to: count a number of instructions in the programmable atomic transaction; and determine the instruction execution limit based upon the number of instructions in the programmable atomic transaction.

In Example 8, the subject matter of Examples 1-7 includes, wherein the request packet and the response are sent over a packet based chiplet network.

Example 9 is a method comprising: receiving a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index fora partition in a memory of the programmable atomic unit; executing instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and sending a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.

In Example 10, the subject matter of Example 9 includes, determining an instruction execution limit for the programmable atomic transaction; initializing an instruction counter; determining whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to determining that the instruction counter exceeds the instruction execution limit, terminating execution of the programmable atomic transaction.

In Example 11, the subject matter of Examples 9-10 includes, wherein determining the instruction execution limit comprises: determining a programmable atomic transaction information data structure from the partition index; and determining the instruction execution limit from the programmable atomic transaction information data structure.

In Example 12, the subject matter of Examples 9-11 includes, wherein prior to receiving the request packet, receiving a request to store instructions in the partition, the request including the instruction execution limit.

In Example 13, the subject matter of Examples 9-12 includes, wherein determining the instruction execution limit comprises: Identifying the instruction execution limit from the request packet.

In Example 14, the subject matter of Examples 9-13 includes, wherein terminating execution of the programmable atomic transaction comprises releasing a lock on a memory location controlled by the memory controller.

In Example 15, the subject matter of Examples 9-14 includes, wherein determining the instruction execution limit comprises: counting a number of instructions in the programmable atomic transaction; and determining the instruction execution limit based upon the number of instructions in the programmable atomic transaction.

In Example 16, the subject matter of Examples 9-15 includes, wherein the request packet and the response are sent over a packet based chiplet network.

Example 17 is a non-transitory machine-readable medium, storing instructions, which when performed by a machine, cause the machine to perform operations comprising: receiving a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index for a partition in a memory of the programmable atomic unit; executing instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and sending a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.

In Example 18, the subject matter of Example 17 includes, wherein the operations further comprise: determining an instruction execution limit for the programmable atomic transaction; initializing an instruction counter; determining whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to determining that the instruction counter exceeds the instruction execution limit, terminating execution of the programmable atomic transaction.

In Example 19, the subject matter of Examples 17-18 includes, wherein the operations of determining the instruction execution limit comprises: determining a programmable atomic transaction information data structure from the partition index; and determining the instruction execution limit from the programmable atomic transaction information data structure.

In Example 20, the subject matter of Examples 17-19 includes, wherein the operations further comprise prior to receiving the request packet, receiving a request to store instructions in the partition, the request including the instruction execution limit.

In Example 21, the subject matter of Examples 17-20 includes, wherein the operations of determining the instruction execution limit comprises: Identifying the instruction execution limit from the request packet.

In Example 22, the subject matter of Examples 17-21 includes, wherein the operations further comprise: wherein terminating execution of the programmable atomic transaction comprises releasing a lock on a memory location controlled by the memory controller.

In Example 23, the subject matter of Examples 17-22 includes, wherein the operations of determining the instruction execution limit comprises: counting a number of instructions in the programmable atomic transaction; and determining the instruction execution limit based upon the number of instructions in the programmable atomic transaction.

In Example 24, the subject matter of Examples 17-23 includes, wherein the request packet and the response are sent over a packet based chiplet network.

Example 25 is an apparatus comprising: means for receiving a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index for a partition in a memory of the programmable atomic unit; means for executing instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and means for sending a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.

In Example 26, the subject matter of Example 25 includes, means for determining an instruction execution limit for the programmable atomic transaction; means for initializing an instruction counter; means for determining whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and means for, responsive to determining that the instruction counter exceeds the instruction execution limit, terminating execution of the programmable atomic transaction.

In Example 27, the subject matter of Examples 25-26 includes, wherein the means for determining the instruction execution limit comprises: means for determining a programmable atomic transaction information data structure from the partition index; and means for determining the instruction execution limit from the programmable atomic transaction information data structure.

In Example 28, the subject matter of Examples 25-27 includes, wherein the apparatus comprises, means for, prior to receiving the request packet, receiving a request to store instructions in the partition, the request including the instruction execution limit.

In Example 29, the subject matter of Examples 25-28 includes, wherein the means for determining the instruction execution limit comprises: means for identifying the instruction execution limit from the request packet.

In Example 30, the subject matter of Examples 25-29 includes, wherein the means for terminating execution of the programmable atomic transaction comprises means for releasing a lock on a memory location controlled by the memory controller.

In Example 31, the subject matter of Examples 25-30 includes, wherein the means for determining the instruction execution limit comprises: means for counting a number of instructions in the programmable atomic transaction; and means for determining the instruction execution limit based upon the number of instructions in the programmable atomic transaction.

In Example 32, the subject matter of Examples 25-31 includes, wherein the request packet and the response are sent over a packet based chiplet network.

Example 33 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-32.

Example 34 is an apparatus comprising means to implement of any of Examples 1-32.

Example 35 is a system to implement of any of Examples 1-32.

Example 36 is a method to implement of any of Examples 1-32.

The above detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention can be practiced. These embodiments are also referred to herein as “examples”. Such examples can include elements in addition to those shown or described. However, the present inventors also contemplate examples in which only those elements shown or described are provided. Moreover, the present inventors also contemplate examples using any combination or permutation of those elements shown or described (or one or more aspects thereof), either with respect to a particular example (or one or more aspects thereof), or with respect to other examples (or one or more aspects thereof) shown or described herein.

In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” can include “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein”. Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The above description is intended to be illustrative, and not restrictive. For example, the above-described examples (or one or more aspects thereof) can be used in combination with each other. Other embodiments can be used, such as by one of ordinary skill in the art upon reviewing the above description. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the above Detailed Description, various features can be grouped together to streamline the disclosure. This should not be interpreted as intending that an unclaimed disclosed feature is essential to any claim. Rather, inventive subject matter can lie in less than all features of a particular disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment, and it is contemplated that such embodiments can be combined with each other in various combinations or permutations. The scope of the invention should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. 

What is claimed is:
 1. An apparatus comprising: A memory controller; a memory array coupled to the memory controller; a programmable atomic unit coupled to the memory controller and comprising a processor, the processor configured to: receive a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index for a partition in a memory of the programmable atomic unit; execute instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and send a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.
 2. The apparatus of claim 1, wherein the processor is further configured to: determine an instruction execution limit o the programmable atomic transaction; initialize an instruction counter; determine whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to a determination that the instruction counter exceeds the instruction execution limit, terminate execution of the programmable atomic transaction.
 3. The apparatus of claim 1, wherein the processor being configured to determine the instruction execution limit comprises being configured to: determine a programmable atomic transaction information data structure from the partition index; and determine the instruction execution limit from the programmable atomic transaction information data structure.
 4. The apparatus of claim 1, wherein the processor is further configured to, prior to receipt of the request packet, receive a request to store instructions in the partition, the request including the instruction execution limit.
 5. The apparatus of claim 1, wherein the processor is configured to determine the instruction execution limit by being configured to: Identify the instruction execution limit from the request packet.
 6. The apparatus of claim 1, wherein the processor is configured to terminate execution of the programmable atomic transaction by being configured to release a lock on a memory location controlled by the memory controller.
 7. The apparatus of claim 1, wherein the processor is configured to determine the instruction execution limit by being configured to: count a number of instructions in the programmable atomic transaction; and determine the instruction execution limit based upon the number of instructions in the programmable atomic transaction.
 8. The apparatus of claim 1, wherein the request packet and the response are sent over a packet based chiplet network.
 9. A method comprising: receiving a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index fora partition in a memory of the programmable atomic unit; executing instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and sending a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.
 10. The method of claim 9, further comprising: determining an instruction execution limit for the programmable atomic transaction; initializing an instruction counter; determining whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to determining that the instruction counter exceeds the instruction execution limit, terminating execution of the programmable atomic transaction.
 11. The method of claim 9, wherein determining the instruction execution limit comprises: determining a programmable atomic transaction information data structure from the partition index; and determining the instruction execution limit from the programmable atomic transaction information data structure.
 12. The method of claim 9, wherein prior to receiving the request packet, receiving a request to store instructions in the partition, the request including the instruction execution limit.
 13. The method of claim 9, wherein determining the instruction execution limit comprises: Identifying the instruction execution limit from the request packet.
 14. The method of claim 9, further comprising: wherein terminating execution of the programmable atomic transaction comprises releasing a lock on a memory location controlled by the memory controller.
 15. The method of claim 9, wherein determining the instruction execution limit comprises: counting a number of instructions in the programmable atomic transaction; and determining the instruction execution limit based upon the number of instructions in the programmable atomic transaction.
 16. The method of claim 9, wherein the request packet and the response are sent over a packet based chiplet network.
 17. A non-transitory machine-readable medium, storing instructions, which when performed by a machine, cause the machine to perform operations comprising: receiving a request packet from a requesting processor, the request packet requesting execution of a programmable atomic transaction at a programmable atomic unit of a memory controller, the request packet including a partition index for a partition in a memory of the programmable atomic unit; executing instructions in the memory, starting at the beginning of the partition, the executing comprising incrementing an instruction counter for every executed instruction; and sending a response to the requesting processor indicating that execution was terminated due to the instruction counter exceeding an instruction execution limit.
 18. The non-transitory machine-readable medium of claim 17, wherein the operations further comprise: determining an instruction execution limit for the programmable atomic transaction; initializing an instruction counter; determining whether, during executing the instructions and prior to a termination instruction being executed, the instruction counter exceeds the instruction execution limit; and responsive to determining that the instruction counter exceeds the instruction execution limit, terminating execution of the programmable atomic transaction.
 19. The non-transitory machine-readable medium of claim 17, wherein the operations of determining the instruction execution limit comprises: determining a programmable atomic transaction information data structure from the partition index; and determining the instruction execution limit from the programmable atomic transaction information data structure.
 20. The non-transitory machine-readable medium of claim 17, wherein the operations further comprise prior to receiving the request packet, receiving a request to store instructions in the partition, the request including the instruction execution limit. 